Skip to content

Adding cleavage benchmarks#404

Open
vue1999 wants to merge 30 commits intoddmms:mainfrom
vue1999:cleavage_benchmark
Open

Adding cleavage benchmarks#404
vue1999 wants to merge 30 commits intoddmms:mainfrom
vue1999:cleavage_benchmark

Conversation

@vue1999
Copy link
Copy Markdown

@vue1999 vue1999 commented Mar 4, 2026

Pre-review checklist for PR author

PR author must check the checkboxes below when creating the PR.

Summary

Adding a benchmark to evaluate the accuracy of predicting cleavage energies of crystalline surfaces.

Linked issue

Resolves #403

Progress

  • Calculations
  • Analysis
  • Application
  • Documentation

Testing

MACE omat, ORB v3

New decorators/callbacks

no

@ElliottKasoar ElliottKasoar added the new benchmark Proposals and suggestions for new benchmarks label Mar 4, 2026
Computational cost
------------------

Medium: benchmark involves only single-point calculations, but for 36,718 slab-bulk pairs.
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

it would be good to give a rough indication of time e.g. hours on gpu and minutes on gpu?

Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes sorry, on GPU it's roughly 5–20 mins, and a few hours on CPUs.

@joehart2001
Copy link
Copy Markdown
Collaborator

joehart2001 commented Mar 22, 2026

Hey @vue1999, thanks for the PR and its looking super good. A few things:

  • ive made some code suggestions to the calc script so we save files in the generalised format. I know there are 30,000 files... but what do you think @ElliottKasoar?
  • ive made some knock on suggestions to the analysis based on these calc changes
  • ive also made suggestions which implement the density scatter plot + structure visualisation, as theres a lot of structures
  • We are also going to in the future add the ability to swithc betwen types of errors e.g. mae and rmse, so ive suggested we just keep mae for now unless you're against this?

Let me know if you've got any ideas or are unsure about any of my suggestions, thanks!

vue1999 and others added 19 commits March 25, 2026 11:42
Co-authored-by: Joseph Hart <92541539+joehart2001@users.noreply.github.com>
Co-authored-by: Joseph Hart <92541539+joehart2001@users.noreply.github.com>
Co-authored-by: Joseph Hart <92541539+joehart2001@users.noreply.github.com>
Co-authored-by: Joseph Hart <92541539+joehart2001@users.noreply.github.com>
Co-authored-by: Joseph Hart <92541539+joehart2001@users.noreply.github.com>
…gy.py

Co-authored-by: Joseph Hart <92541539+joehart2001@users.noreply.github.com>
…gy.py

Co-authored-by: Joseph Hart <92541539+joehart2001@users.noreply.github.com>
…gy.py

Co-authored-by: Joseph Hart <92541539+joehart2001@users.noreply.github.com>
…gy.py

Co-authored-by: Joseph Hart <92541539+joehart2001@users.noreply.github.com>
…gy.py

Co-authored-by: Joseph Hart <92541539+joehart2001@users.noreply.github.com>
Co-authored-by: Joseph Hart <92541539+joehart2001@users.noreply.github.com>
…gy.py

Co-authored-by: Joseph Hart <92541539+joehart2001@users.noreply.github.com>
Co-authored-by: Joseph Hart <92541539+joehart2001@users.noreply.github.com>
Co-authored-by: Joseph Hart <92541539+joehart2001@users.noreply.github.com>
Co-authored-by: Joseph Hart <92541539+joehart2001@users.noreply.github.com>
Co-authored-by: Joseph Hart <92541539+joehart2001@users.noreply.github.com>
…gy.py

Co-authored-by: Joseph Hart <92541539+joehart2001@users.noreply.github.com>
…gy.py

Co-authored-by: Joseph Hart <92541539+joehart2001@users.noreply.github.com>
…gy.py

Co-authored-by: Joseph Hart <92541539+joehart2001@users.noreply.github.com>
vue1999 and others added 9 commits March 25, 2026 11:51
…gy.py

Co-authored-by: Joseph Hart <92541539+joehart2001@users.noreply.github.com>
…gy.py

Co-authored-by: Joseph Hart <92541539+joehart2001@users.noreply.github.com>
…gy.py

Co-authored-by: Joseph Hart <92541539+joehart2001@users.noreply.github.com>
…gy.py

Co-authored-by: Joseph Hart <92541539+joehart2001@users.noreply.github.com>
…gy.py

Co-authored-by: Joseph Hart <92541539+joehart2001@users.noreply.github.com>
…gy.py

Co-authored-by: Joseph Hart <92541539+joehart2001@users.noreply.github.com>
…gy.py

Co-authored-by: Joseph Hart <92541539+joehart2001@users.noreply.github.com>
…gy.py

Co-authored-by: Joseph Hart <92541539+joehart2001@users.noreply.github.com>
…gy.py

Co-authored-by: Joseph Hart <92541539+joehart2001@users.noreply.github.com>
@vue1999
Copy link
Copy Markdown
Author

vue1999 commented Mar 25, 2026

Thanks for the review @joehart2001! Happy to accept all suggestions and fine to keep just MAE for now.

Co-authored-by: Joseph Hart <92541539+joehart2001@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

new benchmark Proposals and suggestions for new benchmarks

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Cleavage energy benchmark

3 participants